From 761c7811685387ac51b579d1765eb6f8fb91c461 Mon Sep 17 00:00:00 2001 From: =?utf8?q?Bastian=20Ils=C3=B8?= Date: Thu, 19 Feb 2015 16:07:09 +0100 Subject: [PATCH] getting-started: move Drawing section to bottom. --- docs/reference/gtk/getting_started.xml | 91 +++++++++++++------------- 1 file changed, 46 insertions(+), 45 deletions(-) diff --git a/docs/reference/gtk/getting_started.xml b/docs/reference/gtk/getting_started.xml index 03bd2d63df..b6d6abed72 100644 --- a/docs/reference/gtk/getting_started.xml +++ b/docs/reference/gtk/getting_started.xml @@ -202,51 +202,6 @@ -
- Drawing - - Many widgets, like buttons, do all their drawing themselves. You - just tell them the label you want to see, and they figure out what font - to use, draw the button outline and focus rectangle, etc. Sometimes, it - is necessary to do some custom drawing. In that case, a #GtkDrawingArea - might be the right widget to use. It offers a canvas on which you can - draw by connecting to the #GtkWidget::draw signal. - - - The contents of a widget often need to be partially or fully redrawn, - e.g. when another window is moved and uncovers part of the widget, or - when tie window containing it is resized. It is also possible to explicitly - cause part or all of the widget to be redrawn, by calling - gtk_widget_queue_draw() or its variants. GTK+ takes care of most of the - details by providing a ready-to-use cairo context to the ::draw signal - handler. - - The following example shows a ::draw signal handler. It is a bit - more complicated than the previous examples, since it also demonstrates - input event handling by means of ::button-press and ::motion-notify - handlers. - - - - - - - - - - - Drawing in response to input - Create a new file with the following content named example-3.c. - FIXME: MISSING XINCLUDE CONTENT - - - You can compile the program above with GCC using: - - gcc `pkg-config --cflags gtk+-3.0` -o example-3 example-3.c `pkg-config --libs gtk+-3.0` - - -
-
Building user interfaces @@ -1041,4 +996,50 @@ example_app_window_init (ExampleAppWindow *win) here.
+ +
+ Custom Drawing + + Many widgets, like buttons, do all their drawing themselves. You + just tell them the label you want to see, and they figure out what font + to use, draw the button outline and focus rectangle, etc. Sometimes, it + is necessary to do some custom drawing. In that case, a #GtkDrawingArea + might be the right widget to use. It offers a canvas on which you can + draw by connecting to the #GtkWidget::draw signal. + + + The contents of a widget often need to be partially or fully redrawn, + e.g. when another window is moved and uncovers part of the widget, or + when tie window containing it is resized. It is also possible to explicitly + cause part or all of the widget to be redrawn, by calling + gtk_widget_queue_draw() or its variants. GTK+ takes care of most of the + details by providing a ready-to-use cairo context to the ::draw signal + handler. + + The following example shows a ::draw signal handler. It is a bit + more complicated than the previous examples, since it also demonstrates + input event handling by means of ::button-press and ::motion-notify + handlers. + + + + + + + + + + + Drawing in response to input + Create a new file with the following content named example-3.c. + FIXME: MISSING XINCLUDE CONTENT + + + You can compile the program above with GCC using: + + gcc `pkg-config --cflags gtk+-3.0` -o example-3 example-3.c `pkg-config --libs gtk+-3.0` + + +
+ -- 2.30.2